Repository navigation
fix(gateway): isolate CID and user-site content - #188
Merged
Merged
Conversation
2 tasks done
This was referenced Oct 1, 2026
Closed
andersalm
marked this pull request as ready for review
October 1, 2026 22:38
This was referenced Oct 1, 2026
Contributor
Author
|
Independent adversarial review (Claude Opus, run by the operator for Anders, 2 October; different model family from the author). |
8 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CID and user-site pages currently run on Home’s origin. This change serves their routes with an opaque sandbox and blocks script API connections. The gateway also refuses opaque or cross-site Home/app API document and resource loads, while existing app fetches and ticketed terminal streams keep their authority checks.
Regression tests cover cached and provider content, every CID alias, site files and admitted bundles, cookie/storage/parent access, refused Home/app reads and writes, unchanged app state, and real form/frame/popup refusal. Chromium runs against the actual gateway router and checks the operator website’s tabs, assets, and command-selection recovery. CI runs the browser regression in the existing test job.
Validation on
6a4b279e0afaace3b35d2c02907a6a0d9b6cacb8:Refs #168 and #173. Target:
develop, based onc9205a742ad612cfa3eedd39f2722df6966328e5. This proof covers direct gateway content; broader Origin, Host and Carrier bootstrap rules remain with #167. CI and irzhywau approval are required before a normal merge.